Skip to content

Name the two parameters BitFieldsToString actually takes - #553

Open
karpovantonme wants to merge 1 commit into
devosoft:masterfrom
karpovantonme:docs-bitfieldstostring-params
Open

Name the two parameters BitFieldsToString actually takes#553
karpovantonme wants to merge 1 commit into
devosoft:masterfrom
karpovantonme:docs-bitfieldstostring-params

Conversation

@karpovantonme

Copy link
Copy Markdown

BitFieldsToString(bits_field_t * bits, size_t count) documents a parameter called field, which the function does not take, and says nothing about the two it does.

Doxygen drops an unknown @param and leaves the real ones undocumented, so the rendered page for this function has no parameter list at all.

The @PARAM line was copied from BitFieldToString above it and still
names a single field. BitFieldsToString takes bits and count, so
Doxygen drops the entry and both parameters render undocumented.

clang -Wdocumentation on bitset_utils.hpp: one warning before, none
after.

Human manager: @karpovantonme
Docstring drafted with Claude Opus, per doc/dev/ai-usage-guidelines.md
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant